fix(helm): do not mix ignore and podSecurity labels#2451
Conversation
Codecov ReportBase: 53.68% // Head: 53.59% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2451 +/- ##
==========================================
- Coverage 53.68% 53.59% -0.09%
==========================================
Files 117 117
Lines 10292 10292
==========================================
- Hits 5525 5516 -9
- Misses 4346 4352 +6
- Partials 421 424 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
good catch! I think we'll need to address this for post-upgrade too? should we add a new container to the existing job instead of a new job? |
Signed-off-by: Mathieu Parent <mathieu.parent@insee.fr>
c67a6c6 to
f01d3c1
Compare
Yes. Done.
No preferred method, I've changed to single-job. |
maxsmythe
left a comment
There was a problem hiding this comment.
LGTM, thank you for the fix!
What this PR does / why we need it:
As a result, using
postInstall.labelNamespace.extraNamespaceswill set restricted PodSecurity on those namespaces. This will most probably render the cluster unusable when it containskube-system.To fix this, we add another job.